Extensible and programmable multi-tenant service architecture

ABSTRACT

An extensible, multi-tenant software-as-a-service business application platform is provided for hosting multiple organizations. Organization services are provided by virtual or physical servers with dedicated data stores assembled in scalable groups. Distributed interaction between components of the scalable groups may enable extensibility and reliability, while changes in locations of organization services are provided to the client(s) for seamless continuation of the client&#39;s access to the services. Customizable and dynamic APIs for accessing each organization&#39;s data and applications isolated from the others and pluggable third party authentication services may also be integrated into the platform.

BACKGROUND

Business efforts strive to respond to customer demands quickly, getproducts to market faster, increase overall profitability, andconsistently outperform the competition. Agility, the ability to meetthese common market challenges, is dependent on a solid businessapplication technology platform. To achieve business agility, amultifaceted, intelligent software infrastructure is needed that isdesigned for application integration.

Business application platforms are typically single tenanted, meaningthat they can host applications only for a single organization and allthe platform resources are dedicated only to that organization. Suchplatforms are typically hosted by the customer and installed anddeployed within their company premises. The cost for deploying andmaintaining such platform may be high and the return-on-investment notoptimized.

On the other hand, designing and managing multi-tenant systems has itsown challenges. In a practical multi-tenant system, each client may havea different schema for connecting to their organization. Furthermore,each client may connect to multiple organizations rendering themanagement of such systems a very complex task from security, trafficmanagement, reliability, and extensibility aspects.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended asan aid in determining the scope of the claimed subject matter.

Embodiments are directed to providing an extensible, multi-tenantsoftware-as-a-service model for serving multiple organizations from asingle platform. A platform according to embodiments may include adiscovery service for providing clients information associated with alocation and configuration of the organization services hosted by theplatform. The client is then enabled to access the organizationservices, which may be hosted in scalable clusters. Location changes maybe provided to the client(s) for uninterrupted access of the client tothe requested service(s).

These and other features and advantages will be apparent from a readingof the following detailed description and a review of the associateddrawings. It is to be understood that both the foregoing generaldescription and the following detailed description are explanatory onlyand are not restrictive of aspects as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example single tenant service model;

FIG. 2 illustrates an example multi-tenant service model;

FIG. 3 illustrates an extensible multi-tenant service architectureaccording to embodiments;

FIG. 4 illustrates example components of an organization service portionof a multi-tenant service;

FIG. 5 is an action diagram illustrating interactions between a clientand components of a multi-tenant service during operations;

FIG. 6 is an example networked environment, where embodiments may beimplemented;

FIG. 7 is a block diagram of an example computing operating environment,where embodiments may be implemented; and

FIG. 8 illustrates a logic flow diagram for a process of providingextensible multi-tenant service to a client.

DETAILED DESCRIPTION

As briefly described above, an extensible multi-tenant businessapplication platform may be provided employing a discovery service andscalable server clusters. In the following detailed description,references are made to the accompanying drawings that form a parthereof, and in which are shown by way of illustrations specificembodiments or examples. These aspects may be combined, other aspectsmay be utilized, and structural changes may be made without departingfrom the spirit or scope of the present disclosure. The followingdetailed description is therefore not to be taken in a limiting sense,and the scope of the present invention is defined by the appended claimsand their equivalents.

While the embodiments will be described in the general context ofprogram modules that execute in conjunction with an application programthat runs on an operating system on a personal computer, those skilledin the art will recognize that aspects may also be implemented incombination with other program modules.

Generally, program modules include routines, programs, components, datastructures, and other types of structures that perform particular tasksor implement particular abstract data types. Moreover, those skilled inthe art will appreciate that embodiments may be practiced with othercomputer system configurations, including hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and the like.Embodiments may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

Embodiments may be implemented as a computer process (method), acomputing system, or as an article of manufacture, such as a computerprogram product or computer readable media. The computer program productmay be a computer storage media readable by a computer system andencoding a computer program of instructions for executing a computerprocess. The computer program product may also be a propagated signal ona carrier readable by a computing system and encoding a computer programof instructions for executing a computer process.

Referring to FIG. 1, diagram 100 of an example single tenant servicemodel is illustrated. As mentioned previously, programmabilityarchitectures for typical business application platforms aresingle-tenanted and suited for on-premise hosted applications.

In such a typical single tenanted platform, client 102 accesses data andbusiness applications associated with a single tenant that is hosted byweb service 106 through networks 104. While networks 104 may be theInternet, it is commonly an intranet type combination of networks. Sincea single tenant is hosted by the service, authentication, security, andother preliminary operations may be performed by the service itself,rather than using a third party service. The location of the servicesdoes typically not change, although redundancy and some load balancingoperations may involve use of multiple servers and/or server clusters.

Thus, operations in a single-tenanted system are relatively simple andstraight forward. However, in today's business world, many organizationsprefer to outsource their business application platforms to entitiesthat can provide efficient, cost-effective, and reliable service. Inorder to streamline their business model and efficiently utilize theirresources, such entities may prefer to host services for multipleorganizations. Furthermore, some clients may be associated with multipleorganizations, in which case it would make sense for the client toaccess all organizations through a single contact point.

FIG. 2 illustrates an example multi-tenant service model 200. In amulti-tenant service, a business application platform hosts services formultiple organizations. Any number of clients 202 may call in to webservice 206 through networks 204, which in this case is more likely tobe the Internet or a combination of diverse networks, for access to dataand applications associated with one or more organizations.

Web service 206 may perform management services and direct clients toorganization specific web services 208. Additionally, web service 206may perform authentication, security check, and similar preliminaryservices optionally using third party services. Organization specificweb services 208 may include scalable clusters, where individualorganizations' operations may be moved for load balancing and otherreasons. Web service 206 may monitor such changes and redirect thecalling client accordingly, such that the change is transparent to theclient.

Clients may be thin or thick clients with additional services optionallyprovided by third party applications in the case of thin clients.Different clients may access different services using distinct schemas.Some of the services may also share the schemas.

The architecture in FIG. 2—for that matter also FIG. 1—is forillustrating an overview of software-as-a-service platforms. Onlyessential components are illustrated for simplicity purposes. Inpractice, such systems include many more components with specific tasksand communication methods. A more detailed discussion of such a platformaccording to embodiments is provided below.

FIG. 3 illustrates an extensible multi-tenant service architecture 300according to embodiments. A software-as-a-service business applicationplatform 320 according to embodiments may be implemented in differentsites and be capable of hosting multiple organizations' data andapplications in each site. Each site installation of the platform 320may be highly scalable enabling high performance and availability ofservices. The sites may be hosted on the Internet or on intranets.

According to some embodiments, the service may use an optional trustedthird party authentication service for authenticating the users (client302) of each organization (e.g. ticket service 312). Independent plug-inauthentication services may also be used for Internet or intranet modes.According to other embodiments, access to each organization's data andoperations may be restricted based on security roles and privileges andorganization membership.

According to some implementations, each organization's data andapplications may be isolated from the others and accessed through a setof dedicated of APIs. The APIs may enable developers to access andmodify business data as well as define/invoke/modify business processesand logic remotely over the Internet. The APIs may be automaticallygenerated and dynamic, so that whenever a new organization is added toor removed from the platform, the APIs can automatically adjust. TheAPIs may also be customizable allowing custom objects and operations tobe added to each organization separate from other organizations.

Discovery service 322 provides authentication and organization discoveryservices enabling a client 302 to sign in into the platform 320 anddiscover all the organizations that he/she is a member of. Discoveryservice 322 may provide detailed configuration data about eachorganization including its location within the platform for directaccess and other configuration information. The configurationinformation may be stored in and retrieved from configuration store 324.A user (client) can be a member of one or more organizations hosted in asite. The discovery service 322 may operate in multiple authenticationmodes. Each authentication mode may have its own dedicated endpointenabling the client to specify what authentication should be used.

According to further embodiments, each API endpoint may serve multipleorganizations. Each call to the API may identify the target organizationintended to reach. The discovery service 322 may use configuration store324 to retrieve organization configuration data. An administrator may beenabled to access and maintain the configuration store 324.

Organization data and operations may be placed in a plurality ofscalable groups (service locations 1, 2, etc.) available within aservice cluster 330 of the platform 320. An organization's location maychange and move between the scalable groups for load balancing purposes.The extensible multi-tenant service model is dynamic in a sense that itcan locate the target organization even after a move. Each servicelocation (332, 334. . . ) may include one or more virtual or physicalservers providing the services.

FIG. 4 illustrates example components of an organization service portionof a multi-tenant service. As mentioned above, scalable server clusters430 are at the core of an extensible multi-tenant software-as-a-serviceplatform. According to some embodiments, server clusters 430 may includea group of virtual or physical web servers 431 that receive the clientrequest, handle synchronous requests, and manage access to organizationdatabases 433. A particular server among web servers 431 may be assignedto the client by random selection, according to a predefined algorithm(e.g. a load balancing algorithm), and the like. Organization databases433 may include physical or virtual data stores for each organization(or tenant) served by the platform. For example, a financial servicessystem may include separate databases for each of the participatingfinancial organizations (banks, etc.) that store account information,account access information, and so on. Information about the individualdatabases, their configuration, any redundancies, and the like, may bestored in configuration store 324 of FIG. 3.

According to other embodiments, a locator service (not shown) mayprovide information about which database(s) may be used by the webservers. Web servers 433 may also place asynchronous service requests inqueues to be handled by asynchronous servers 435 in conjunction withorganization databases 433. As a client request comes up in the queue,one of the asynchronous servers 435 may be contacted for processing therequest. A relationship between the asynchronous servers and theindividual organization databases may be a distributed one, where eachserver may work with any one of the databases. This distributedinteraction between the asynchronous servers and the organizationdatabases may provide the ability to automatically recover from failuresin the asynchronous processing machines by allowing the databases toconnect to another available server when one fails.

Due to the independent distribution of synchronous and asynchronous workand the interaction between the servers and the databases, any part ofthe server cluster 430 is scalable. Thus, multiple instances of theservers (and/or databases) may be provided to address increasedworkload, additional organizations, data capacity, and so on.

FIG. 5 is an action diagram illustrating interactions between a clientand components of a multi-tenant service during operations. Theinteractions in action diagram 500 illustrate an example operation withspecific steps. Interactions in a multi-tenant platform according toembodiments may include different exchanges with fewer or additionalsteps, as well as a different order of interactions.

According to the example operation, client 504 initiates a call byrequesting a site policy from discovery service 506. Discovery service506 responds with the site policy, which may identify an optional ticketservice 502 (e.g. for authentication). If the optional third partyticket service 502 is used, client 504 may send a ticket request to theticket service 502, and receive the service ticket if the client'scredentials are confirmed for access to a requested organization(tenant).

Client 504 then submits a site ticket request with the service ticketfrom ticket service 502 to discovery service 506. Discovery service 506responds with the site ticket. Client 504 may then submit a list ofrequested organizations, to which discovery service 506 responds withthe list of locations of the requested organizations and otherconfiguration information (schema, etc.). Subsequently, client 504 mayaccess the target organizations through organization services 508 usingthe location and configuration information provided by the discoveryservice 506. As indicated previously, the location of organizationservices may change due to scaling, load balancing, and so on. Discoveryservice 506 may update the client with the changed location informationsuch that the client's access to the organization service can continueseamlessly.

The scalable multi-tenant systems and operations described in FIG. 3,through FIG. 5 are exemplary for illustration purposes. A system forextensible multi-tenant services may be implemented with additional orfewer components and operations using the principles described herein.

FIG. 6 is an example networked environment, where embodiments may beimplemented. Extensible multi-tenant service systems may be implementedin a distributed manner over a number of physical and virtual clientsand servers. They may also be implemented in un-clustered systems orclustered systems employing a number of nodes communicating over one ormore networks (e.g. network(s) 610).

Such a system may comprise any topology of servers, clients, Internetservice providers, and communication media. Also, the system may have astatic or dynamic topology. The term “client” may refer to a clientapplication or a client device. While a networked system implementingextensible multi-tenant services may involve many more components,relevant ones are discussed in conjunction with this figure.

Requests for access may come from tenants using individual clientdevices 602-606 or application server 608 in a networked multi-tenantsystem. Such a system may also be implemented, in one or more servers(e.g. servers 612, 614) and accessed by the client devices (orapplications). One or more web servers (physical or virtual) such as webserver 612 may receive the requests and direct them to the appropriateresource. The resources may include scalable server clusters withsynchronous and asynchronous server, organization databases, and othercomponents.

Organization databases may be embodied in a single data store such asdata store 618 or distributed over a number of data stores. Dedicateddatabase servers (e.g. database server 616) may be used to coordinatedata retrieval and storage in one or more of such data stores.

Network(s) 610 may include a secure network such as an enterprisenetwork, an unsecure network such as a wireless open network, or theInternet. Network(s) 610 provide communication between the nodesdescribed herein. By way of example, and not limitation, network(s) 610may include wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media.

Many other configurations of computing devices, applications, datasources, data distribution systems may be employed to implement anextensible multi-tenant service platform. Furthermore, the networkedenvironments discussed in FIG. 6 are for illustration purposes only.Embodiments are not limited to the example applications, modules, orprocesses.

FIG. 7 and the associated discussion are intended to provide a brief,general description of a suitable computing environment in whichembodiments may be implemented. With reference to FIG. 7, a blockdiagram of an example computing operating environment is illustrated,such as computing device 700. In a basic configuration, the computingdevice 700 may be a server providing management services associated withan extensible multi-tenant service and typically include at least oneprocessing unit 702 and system memory 704. Computing device 700 may alsoinclude a plurality of processing units that cooperate in executingprograms. Depending on the exact configuration and type of computingdevice, the system memory 704 may be volatile (such as RAM),non-volatile (such as ROM, flash memory, etc.) or some combination ofthe two. System memory 704 typically includes an operating system 705suitable for controlling the operation of a networked personal computer,such as the WINDOWS® operating systems from MICROSOFT CORPORATION ofRedmond, Wash. The system memory 704 may also include one or moresoftware applications such as program modules 706, Web services 722, adiscovery service 724 within web services 722, and an optional locatorservice 726.

Web services 722 may be a separate application or an integral module ofa hosted multi-tenant service platform that provides data and processingservices to client applications associated with computing device 700.Discovery service 724 may provide location and configuration informationassociated with individual organization (tenant) services to a clientrequesting access to those. Optional locator service 726 may provideservices associated with determining a purpose of the service and whichdatabases to use for web servers, as well as asynchronous processingservers, as described previously. This basic configuration isillustrated in FIG. 7 by those components within dashed line 708.

The computing device 700 may have additional features or functionality.For example, the computing device 700 may also include additional datastorage devices (removable and/or non-removable) such as, for example,magnetic disks, optical disks, or tape. Such additional storage isillustrated in FIG. 7 by removable storage 709 and non-removable storage710. Computer storage media may include volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Systemmemory 704, removable storage 709 and non-removable storage 710 are allexamples of computer storage media. Computer storage media includes, butis not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and which can be accessed by computingdevice 700. Any such computer storage media may be part of device 700.Computing device 700 may also have input device(s) 712 such as keyboard,mouse, pen, voice input device, touch input device, etc. Outputdevice(s) 714 such as a display, speakers, printer, etc. may also beincluded. These devices are well known in the art and need not bediscussed at length here.

The computing device 700 may also contain communication connections 716that allow the device to communicate with other computing devices 718,such as over a wireless network in a distributed computing environment,for example, an intranet or the Internet. Other computing devices 718may include server(s) that execute applications associated with alocation service or other services. Communication connection 716 is oneexample of communication media. Communication media may typically beembodied by computer readable instructions, data structures, programmodules, or other data in a modulated data signal, such as a carrierwave or other transport mechanism, and includes any information deliverymedia. The term “modulated data signal” means a signal that has one ormore of its characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. The term computer readable media asused herein includes both storage media and communication media.

The claimed subject matter also includes methods. These methods can beimplemented in any number of ways, including the structures described inthis document. One such way is by machine operations, of devices of thetype described in this document.

Another optional way is for one or more of the individual operations ofthe methods to be performed in conjunction with one or more humanoperators performing some. These human operators need not be collocatedwith each other, but each can be only with a machine that performs aportion of the program.

FIG. 8 illustrates a logic flow diagram for process 800 of providingextensible multi-tenant service to a client. Process 800 may beimplemented as part of a software-as-a-service business applicationplatform.

Process 800 begins with operation 802, where a request for accessing oneor more organizations is received from a client along with the clientcredentials. As described previously, clients of a multi-tenant hostedservice are typically associated with organizations or tenants each ofwhich has a service including a dedicated database within the system.Prior to receiving the request, the client may optionally use a thirdparty authentication service. Processing advances from operation 802 todecision operation 804.

At decision operation 804, a determination is made whether the client isauthenticated. The determination may also include a check of whether therequested organization(s) are hosted by the multi-tenant serviceplatform. If the client is authenticated, the process advances tooperation 806. Otherwise, processing moves to a calling process forfurther actions.

At operation 806, a location of the requested organization service isdetermined. Processing moves from operation 806 to operation 808, wherethe location of the organization service is provided to the client foraccess. Additional configuration information may also be provided alongwith the location information. After operation 808, processing moves todecision operation 810.

At decision operation 810, a determination is made whether the locationof the organization service is changed due to scaling, load balancing,and so on. If a change in the location is determined, processing movesto operation 812. Otherwise, processing moves to a calling process forfurther actions.

At operation 812, the change in the location of the organization serviceis provides to the client such that the client's access to the servicecan continue seamlessly. After operation 812, processing moves to acalling process for further actions.

The operations included in process 800 are for illustration purposes.Providing extensible multi-tenant service to a client may be implementedby similar processes with fewer or additional steps, as well as indifferent order of operations using the principles described herein.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theembodiments. Although the subject matter has been described in languagespecific to structural features and/or methodological acts, it is to beunderstood that the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims and embodiments.

1. A method to be executed at least in part in a computing device forproviding an extensible multi-tenant service platform, the methodcomprising: receiving a request for access from a client, wherein eachclient is associated with at least one organization service hosted bythe platform; determining a location of the organization service,wherein the organization services are organized in scalable groupswithin the platform; providing the location of the organization serviceto the client to enable access to the organization service; and if thelocation of the organization service changes during the access,providing the changed location to the client for continued access of theclient to the organization service.
 2. The method of claim 1, furthercomprising: authenticating the client prior to providing the location ofthe organization service using one of an integrated authenticationservice and a third party authentication service.
 3. The method of claim2, wherein the client's access to the requested organization service isrestricted based on at least one from a set of: a security status ofclient connection, a client credential, and an organization membership.4. The method of claim 2, further comprising: providing a plurality ofauthentication modes, wherein each authentication mode includes adedicated endpoint such that the client is enabled to specify a desiredauthentication mode.
 5. The method of claim 1, further comprising:providing configuration information to the client associated with theclient's access to the requested organization service.
 6. The method ofclaim 1, wherein the scalable groups are configured to enable a verticaland a horizontal extensibility of applications associated withorganization services hosted by the platform.
 7. The method of claim 1,wherein the platform is arranged to provide metadata access fororganization services hosted by the platform.
 8. A system for hostingextensible multi-tenant services, comprising: a discovery serviceconfigured to: receive a request for access from a client associatedwith at least one organization service hosted by the system; determine alocation of the requested organization service; and provide the locationof the organization service to the client to enable access to theorganization service; a plurality of scalable service clustersconfigured to provide the organization service; and a configurationstore associated with the discovery service arranged to storeconfiguration and location information associated with the plurality ofservice clusters such that a change in the location of the organizationservice during the client's access to the organization service isprovided to the client for continued access of the client to theorganization service.
 9. The system of claim 8, wherein the discoveryservice and the service clusters are provided as web services.
 10. Thesystem of claim 8, wherein the discovery service is further configuredto authenticate the client employing a plurality of authentication modesthrough a pluggable authentication service.
 11. The system of claim 8,further comprising: a plurality of dedicated Application ProgrammingInterfaces (APIs) configured to provide access to the organizationservices such that data and applications associated with eachorganization service are isolated from other organization services. 12.The system of claim 11, wherein the APIs are customizable such that auser with permission is enabled to add at least one of a custom objectand a custom operation to a selected organization service.
 13. Thesystem of claim 11, wherein the APIs are configured to enable users withpermission to perform actions including: modify data associated with anorganization service; define one of a process and a logic associatedwith the organization service; invoke one of a process and a logicassociated with the organization service; and modify one of a processand a logic associated with the organization service.
 14. The system ofclaim 11, wherein the APIs are dynamically generated such that the APIsare adapted to one of an addition and a removal of an organizationservice in the system.
 15. The system of claim 11, wherein the serviceclusters include a plurality of web servers, organization databases, andasynchronous processing servers configured to interact in a distributedmanner.
 16. The system of claim 15, wherein at least a portion of theplurality of web servers, organization databases, and asynchronousprocessing servers is virtual.
 17. The system of claim 15, whereinmultiple instances of the plurality of web servers, organizationdatabases, and asynchronous processing servers are provided to enablescalability, load balancing, and failure recovery.
 18. Acomputer-readable storage medium with instructions stored thereon forproviding an extensible multi-tenant service platform, the instructionscomprising: receiving a request for access from a client associated withat least one organization service hosted by the platform, wherein therequest includes a credential of the client; determining a list oforganization services available to the client based on the client'scredential; providing the list of organization services to the client;receiving a request for accessing at least one organization service fromthe list; determining a location of the at least one requestedorganization service, wherein the organization services are provided byscalable service clusters hosted by the platform; providing the locationof the at least one organization service to the client to enable accessto the organization service; and if the location of the organizationservice changes during the access, providing the changed location to theclient for continued access of the client to the organization service.19. The computer-readable storage medium of claim 18, wherein theinstructions further comprise: authenticating the client using at leastone authentication mode for each organization service requested by theclient.
 20. The computer-readable storage medium of claim 18, whereinthe instructions further comprise: dynamically providing a set ofdedicated APIs for each organization service hosted by the platform toenable modification of at least one of data and processes associatedwith each organization service by an administrator such that the APIsare adapted to one of an addition and a removal of an organizationservice in the platform.